home *** CD-ROM | disk | FTP | other *** search
/ Clickx 115 / Clickx 115.iso / software / tools / windows / tails-i386-0.16.iso / live / filesystem.squashfs / usr / share / i2p / docs / ahelper-conflict-header.ht < prev    next >
Encoding:
Text File  |  2012-10-27  |  1.3 KB  |  32 lines
  1. HTTP/1.1 409 Conflict
  2. Content-Type: text/html; charset=UTF-8
  3. Cache-control: no-cache
  4. Connection: close
  5. Proxy-Connection: close
  6.  
  7. <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
  8. <html><head>
  9. <title>I2P Warning: Destination key conflict</title>
  10. <link rel="shortcut icon" href="http://proxy.i2p/themes/console/images/favicon.ico">
  11. <link href="http://proxy.i2p/themes/console/default/console.css" rel="stylesheet" type="text/css">
  12. </head>
  13. <body>
  14. <div class="logo">
  15.  <a href="http://127.0.0.1:7657/" title="Router Console"><img src="http://proxy.i2p/themes/console/images/i2plogo.png" alt="I2P Router Console" border="0"></a><hr>
  16.  <a href="http://127.0.0.1:7657/config.jsp">Configuration</a> <a href="http://127.0.0.1:7657/help.jsp">Help</a> <a href="http://127.0.0.1:7657/susidns/">Addressbook</a>
  17. </div>
  18. <div class="warning" id="warning">
  19. <h3>Warning: Destination Key Conflict</h3>
  20. <p>
  21. The addresshelper link you followed specifies a different destination key
  22. than a host entry in your host database.
  23. Someone could be trying to impersonate another eepsite,
  24. or people have given two eepsites identical names.
  25. </p>
  26. <p>
  27. You can resolve the conflict by considering which key you trust,
  28. and either discarding the addresshelper link,
  29. discarding the host entry from your host database,
  30. or naming one of them differently.
  31. </p>
  32.